Configure Managed Change

Under normal circumstances, you should not need to configure the behavior of the Managed Change functions. The default settings are adequate for most environments. However, they can be configured to meet unique requirements or for compatibility with customization.

The Managed Change settings are described in the following table.

To configure the Managed Change settings:

1. In Configurator, expand Environment in the configuration tree and select Vault Settings. The settings for each application link appear in property pages in the right pane.
2. Click the Settings tab. The Settings page appears in the right pane.

3. Click the Edit button to modify the settings.

   Note:

   To export the settings file to your computer, click the Export button. This can be useful if you would rather edit the file in your favorite text editor. You can then copy your changes to the Clipboard and paste them into Configurator.

4. Locate the section of the file titled [ProjectWorkflow] and locate the setting that you want to configure. Create the section and setting if they do not already exist.
5. To change the default behavior, set the value of the setting to one of the values described for the setting in the following table. If the setting begins with a semicolon (;) character, the setting is disabled. Enable the setting by removing the semicolon.
6. Click OK to save your changes. The setting becomes effective the next time that the client applications are started or open the vault.

Managed Change settings

Setting	Description
AllowWorkflowAcrossProjects	If set to Y (the default is N), allows a batch of documents that reside in separate project folders to be routed together in the same operation. Enable this setting with care because the documents may have references that reside in other projects and the results might not be as expected.
CreateProjectCopyInWebAccessMode	If set to Y (the default is N) and a project copy is made, this setting suppresses the Reference Explorer dialog box in the PowerUser client and also suppresses the resolution and copying of referenced documents. This causes the PowerUser to behave similar to PowerWeb for this operation. This can dramatically shorten the time required to create project copies that reference many other documents. This setting is the most beneficial in vaults that contain many references to asset tags related to a maintenance management system. We do not recommend enabling this option in vaults that do not contain asset tags but instead references are primarily to assembly parts or related documents. This setting is located in the [Vault] section , not the [ProjectWorkflow] section.
CreateProjectCopyForRetired	If set to Y, project copies can be made from retired documents. If set to N (default), retired documents cannot be copied.
CreateProjectCopyInSelectedFolder	If set to Y (default), Meridian creates project copies in the project folder that is selected by the user. If customized event procedures attempt to move the document to a different location, folder locking errors can occur if more than one procedure is active at the same time. When set to N (No), the copy is made without any parent folder. Meridian then moves the document to its destination folder as calculated by the Field-Path definition, if it is defined. If the Field-Path definition is not defined, the copy is moved to the folder that is current at the time that the copy is made.
DiscardProjectRefs	Controls the disposition of references between project copies made in the same project folder when one of the project copies is discarded. The possible values are: 0 – discard all references (default) 1 – do not discard references made by the CAD links 2 – do not discard custom (manual) references 3 – do not discard any references. Note: When set to a value other than 0, references between project copies will be redirected to the master document if one of the project copies is discarded from the project. If the remaining project copy is released from the project, both master documents will then be related by a reference that did not exist prior to the project copies being made. In some scenarios, such as assembly relationships, this might be desirable. In other scenarios, such as custom references, this might not be desirable. Carefully consider and test all scenarios with all available reference types and your business processes before changing this setting in a production environment.
DoNotRerouteRefs2Master	If set to Y (Yes), incoming references are not rerouted to the master document after a project copy is released. The references remain routed to the inactive project copy. The default is N (No).
RtmRenditionAction	Controls the disposition of the master document rendition when a project copy is released as a new revision of the master document. The possible values are: 0 – copy the rendition from the project copy to the master document. This is the default. 1 – queue the master document in Publisher to regenerate the master document rendition. Use this setting if Publisher is configured to add a watermark to the previous version of the rendition 2 – do nothing. This setting is provided for compatibility with custom event handlers that determine what is done.